[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes#245183
Merged
nastasha-solomon merged 11 commits intoDec 4, 2025
Conversation
Contributor
🔍 Preview links for changed docs |
2 tasks
Contributor
💚 Build Succeeded
|
ymao1
approved these changes
Dec 4, 2025
nastasha-solomon
added a commit
to elastic/docs-content
that referenced
this pull request
Dec 4, 2025
…nts for reporting (#4211) ## Summary Contributes to http://github.com/elastic/docs-content-internal/issues/514 by updating the 9.x docs. More specifically, this PR modifies the note about CCS priv requirements for reporting by: - Updating the `applies_to` tag to indicate that the information is relevant to users on 9.1+ - In the example, replaces the term "leader" with "local" ### Corresponding fixes - 8.19 reporting docs and Kibana release notes: elastic/kibana#245182 - 9.1 Kibana release notes: elastic/kibana#245183 ## Generative AI disclosure 1. Did you use a generative AI (GenAI) tool to assist in creating this contribution? - [ ] Yes - [x] No ## Preview - [Configure Kibana reporting | Configuration overview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4211/deploy-manage/kibana-reporting-configuration#configuration-overview) - [Automatically generate reports](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4211/explore-analyze/report-and-share/automating-report-generation)
nastasha-solomon
added a commit
that referenced
this pull request
Dec 4, 2025
…quirements for reporting and updates Kib 8.19 release notes (#245182) ## Summary Contributes to http://github.com/elastic/docs-content-internal/issues/514 by updating the 8.19 reporting docs and Kibana release notes. More specifically, this PR: - Modifies the the third sentence in note about CCS priv requirements for reporting. Replaces the term "leader" with "local". - Adds breaking change entries to the 8.19 Kibana release notes and the Kibana upgrade notes. This should make the change more visible to users who are upgrading to 8.19. ### Corresponding fixes - 9.1 reporting docs: elastic/docs-content#4211 - 9.1 Kibana release notes: #245183 ## Previews - [Automatically generate reports](https://kibana_bk_245182.docs-preview.app.elstc.co/guide/en/kibana/8.19/automating-report-generation.html) - Updated note - [Configure reporting in Kibana | Grant users access to reporting](https://kibana_bk_245182.docs-preview.app.elstc.co/guide/en/kibana/8.19/secure-reporting.html#grant-user-access) - Updated second note in the intro section of the page - [Upgrade notes | Breaking changes | Kibana platform](https://kibana_bk_245182.docs-preview.app.elstc.co/guide/en/kibana/8.19/breaking-changes-summary.html#_kibana_platform) - Added entry titled "[Sharing & Reporting] API keys are used for authenticating report generation requests. (8.19)" - [Kibana 8.19.0 | Breaking changes](https://kibana_bk_245182.docs-preview.app.elstc.co/guide/en/kibana/8.19/release-notes-8.19.0.html#breaking-changes-8.19.0) - Added entry titled "API keys are used for authenticating report generation requests" --------- Co-authored-by: Ying Mao <ying.mao@elastic.co>
Contributor
|
Starting backport for target branches: 9.1, 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 4, 2025
…reporting to 9.1 Kibana release notes (elastic#245183) ## Summary Contributes to http://github.com/elastic/docs-content-internal/issues/514 by documenting the breaking change to CCS-based reporting in the 9.1 Kibana release notes. Also took this opportunity to remove the `%` char from some breaking change descriptions (it was commenting out lines). ### Corresponding fixes - 8.19 reporting docs and Kibana release notes: elastic#245182 - 9.1 reporting docs: elastic/docs-content#4211 ## Previews - [9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes) - see the second item in the section (cherry picked from commit a7a6130)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Member
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
nastasha-solomon
added a commit
to nastasha-solomon/kibana
that referenced
this pull request
Dec 4, 2025
…reporting to 9.1 Kibana release notes (elastic#245183) ## Summary Contributes to http://github.com/elastic/docs-content-internal/issues/514 by documenting the breaking change to CCS-based reporting in the 9.1 Kibana release notes. Also took this opportunity to remove the `%` char from some breaking change descriptions (it was commenting out lines). ### Corresponding fixes - 8.19 reporting docs and Kibana release notes: elastic#245182 - 9.1 reporting docs: elastic/docs-content#4211 ## Previews - [9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes) - see the second item in the section (cherry picked from commit a7a6130) # Conflicts: # docs/release-notes/breaking-changes.md
nastasha-solomon
added a commit
that referenced
this pull request
Dec 4, 2025
…based reporting to 9.1 Kibana release notes (#245183) (#245278) # Backport This will backport the following commits from `main` to `9.1`: - [[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)](#245183) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nastasha Solomon","email":"79124755+nastasha-solomon@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-04T16:49:32Z","message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:version","v9.1.0","v9.2.0","v9.3.0"],"title":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes","number":245183,"url":"https://github.com/elastic/kibana/pull/245183","mergeCommit":{"message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/245276","number":245276,"state":"OPEN"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245183","number":245183,"mergeCommit":{"message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4"}}]}] BACKPORT-->
kibanamachine
added a commit
that referenced
this pull request
Dec 4, 2025
…based reporting to 9.1 Kibana release notes (#245183) (#245276) # Backport This will backport the following commits from `main` to `9.2`: - [[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)](#245183) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nastasha Solomon","email":"79124755+nastasha-solomon@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-12-04T16:49:32Z","message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:version","v9.1.0","v9.2.0","v9.3.0"],"title":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes","number":245183,"url":"https://github.com/elastic/kibana/pull/245183","mergeCommit":{"message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.2"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245183","number":245183,"mergeCommit":{"message":"[DOCS][ResponseOps][Alerting][9.1]: Add breaking change to CCS-based reporting to 9.1 Kibana release notes (#245183)\n\n## Summary\n\nContributes to\nhttp://github.com/elastic/docs-content-internal/issues/514 by\ndocumenting the breaking change to CCS-based reporting in the 9.1 Kibana\nrelease notes.\n\nAlso took this opportunity to remove the `%` char from some breaking\nchange descriptions (it was commenting out lines).\n\n### Corresponding fixes\n- 8.19 reporting docs and Kibana release notes:\nhttps://github.com//pull/245182\n- 9.1 reporting docs: https://github.com/elastic/docs-content/pull/4211\n\n## Previews\n\n-\n[9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes)\n- see the second item in the section","sha":"a7a6130042f450e4ffcd560b8452bc9fdd7c43b4"}}]}] BACKPORT--> Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
…reporting to 9.1 Kibana release notes (elastic#245183) ## Summary Contributes to http://github.com/elastic/docs-content-internal/issues/514 by documenting the breaking change to CCS-based reporting in the 9.1 Kibana release notes. Also took this opportunity to remove the `%` char from some breaking change descriptions (it was commenting out lines). ### Corresponding fixes - 8.19 reporting docs and Kibana release notes: elastic#245182 - 9.1 reporting docs: elastic/docs-content#4211 ## Previews - [9.1](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/245183/release-notes/breaking-changes#kibana-9.1.0-breaking-changes) - see the second item in the section
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Contributes to http://github.com/elastic/docs-content-internal/issues/514 by documenting the breaking change to CCS-based reporting in the 9.1 Kibana release notes.
Also took this opportunity to remove the
%char from some breaking change descriptions (it was commenting out lines).Corresponding fixes
Previews